fix: tolerate punctuation in voice activation finish phrase - #1219

Summary

• Fix voice activation finish commands when local ASR inserts punctuation inside the phrase, such as 完成，语音录入。.
• Apply the same NFKC-aware punctuation handling to transcript cleanup so the finish phrase is removed without dropping punctuation from the spoken body.
• Add regression coverage for Chinese punctuation, full-width punctuation, whitespace, and suffix-only matching.

Refs #1003

Why retain the diagnostic probes?

There is no further tester evidence confirming whether the intermittent recognition crash has been resolved or simply has not reproduced. We therefore retain the existing privacy-safe P1–P6 diagnostic probes rather than treating the absence of a new report as proof of a fix. If the issue recurs, these lifecycle and timing records, together with the matching Windows EXE/PDB, will provide evidence for further investigation. The probes do not record audio or transcript content. They should be removed only after sufficient real-device verification; passing CI alone does not establish that the intermittent crash is fixed.

Beta synchronization

Merged beta at 8e8b3dbd and resolved the overlapping voice-activation conflicts, preserving the newer implementation, regression tests, diagnostic probes, and Windows symbols already merged via #1240. Application source now matches beta; the only remaining branch-only difference is the pre-existing Android workflow repository-metadata setting. This synchronization does not introduce another behavioral fix or claim that all of #1003 is resolved.

Verification

Current commit: e3b5c6ba8c8eaa60b29b47197f04dbcf753df711.

• git diff --check and staged whitespace checks passed; no unresolved merge conflicts remain.
• All compilation, tests, and packaging run in GitHub Actions, not locally.
• PR CI: passed, including Windows, macOS, Linux, Android, Harmony, and UI motion. MSRV is skipped by the workflow's existing condition.
• Native capsule checks: passed on Windows and macOS.
• Branch CI: Windows, Linux, Android, Harmony, and UI motion passed. macOS initially did not acquire a hosted runner (runner_id=0, no steps); GitHub reports macOS ARM capacity constraints. The single targeted retry also ended without acquiring a runner (runner_id=0, no steps), with the same capacity annotations. The branch workflow therefore ended in failure due to unavailable hosted capacity, not an executed test failure; it has not passed as a whole. No further automatic retries are queued.
• Desktop builds: Windows and macOS Intel jobs, including artifact uploads and post-build steps, passed. macOS ARM initially did not acquire a hosted runner and was cancelled with the same capacity annotation; the single targeted ARM retry also ended without a runner (runner_id=0, no steps), with the same capacity annotations. The overall workflow ended in failure; macOS ARM packaging remains unverified. No further automatic retries are queued.
  • Windows x64 test artifact, retaining matching EXE/PDB. GitHub artifact metadata confirms the current commit and reports ZIP digest sha256:891f00384ee41962948aa54d29e8b817beee9301ec7292ae0590e7908961e4af.
  • macOS Intel artifact.
• Android arm64 build: passed; release APK artifact.

The PR remains a draft for the author to mark ready after verification. No claim is made that the intermittent crash has passed real-device verification.

🤖 Generated with Claude Code